Qhost

Category: trojan · Aliases: Qhost, Trojan:Win32/Qhost, TROJ_QHOST, DNSChanger.Qhost, Win32/Qhost, Trojan.Qhost, Qhosts Redirector · Sample count (EMBER 2018): 1,722 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2003Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Traffic Hijacking and Ad Fraud🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Trojan:Win32/Qhost (cataloged widely across security telemetry as TROJ_QHOST, DNSChanger.Qhost, or Win32/Qhost) is a classic and persistent DNS-tampering trojan designed to hijack internet traffic by modifying the Windows HOSTS configuration file (%SystemRoot%\System32\drivers\etc\hosts).

Table of Contents

Overview

Trojan:Win32/Qhost (cataloged widely across security telemetry as TROJ_QHOST, DNSChanger.Qhost, or Win32/Qhost) is a classic and persistent DNS-tampering trojan designed to hijack internet traffic by modifying the Windows HOSTS configuration file (%SystemRoot%\System32\drivers\etc\hosts). Deployed through software cracks, malicious email attachments, and exploit kits, Qhost modifies local name-resolution mappings to redirect web browser traffic away from legitimate domains toward attacker-controlled phishing servers, fraudulent advertising syndicates, and credential-harvesting landing pages. Crucially, Qhost systematically appends hundreds of entries mapping security vendor domains (including Microsoft, Trend Micro, Kaspersky, Symantec, and Malwarebytes) to loopback (127.0.0.1) or unreachable addresses, effectively neutralizing automatic antivirus signature updates and preventing victims from downloading remediation software.

Known aliases

Threat reports may refer to this family under multiple names:

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Win32 Hosts Modifier Dns Hijacker Lineage

Known Derivatives & Downstream Variants: Troj_Qhost.Ss · Trojan:Win32/Qhosts.Gen · Win32/Qhost.B

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-RVMRegistry Value Modification AnalysisDetectT1112Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.
D3-STASecurity Tool Anti-Tamper EnforcementHardenT1562.001Block unauthorized modification of antivirus registry flags and prevent stopping security agent services.

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_QHOST_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Qhost"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "qhost" ascii wide nocase
        $s2 = "qhost" ascii wide nocase
        $s3 = "trojan:win32/qhost" ascii wide nocase
        $s4 = "troj_qhost" ascii wide nocase
        $s5 = "dnschanger.qhost" ascii wide nocase
        $s6 = "win32/qhost" ascii wide nocase
        $s7 = "trojan.qhost" ascii wide nocase
        $s8 = "qhosts redirector" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Qhost (Trojan) Execution & Triage
id: d54227aa-4544-5069-9d47-4a3ef2de446f
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Qhost malware family. Detects suspicious execution from temporary user
  directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/qhost
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1565_001
- attack.t1562_001
- attack.t1112
- attack.t1071_001
- attack.t1547_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_QHOST_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Qhost tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "qhost" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Qhost from retrieving secondary stage payloads.
  2. Capture process memory triage to detect and terminate malicious threads injected by Qhost into legitimate system processes such as explorer.exe or svchost.exe.
  3. Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Qhost persistence hooks.
  4. Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
  5. Rotate all credentials, domain user passwords, and session cookies active on the system during the Qhost execution timeframe.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Qhost dropper; always verify that secondary payloads and persistence hooks have been eradicated.
  2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Qhost until memory triage is complete.
  3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

Frequently Asked Questions

What is Trojan:Win32/Qhost?

Qhost is a DNS-hijacking Trojan that overwrites the Windows HOSTS file to redirect users to phishing sites and block access to cybersecurity update servers.

Why does Qhost target the Windows HOSTS file?

Windows checks the local HOSTS file before sending DNS queries over the network; poisoning this file allows the malware to redirect specific domain names instantly.

How does Qhost prevent users from cleaning the infection?

Qhost maps domains belonging to antivirus companies and security blogs to 127.0.0.1, blocking antivirus updates and preventing users from downloading removal utilities.

Why do browsers remain broken even after Qhost is deleted?

Simply deleting the Trojan executable leaves the poisoned HOSTS file and cached DNS entries intact, requiring manual or automated restoration of default settings.

How do you completely repair a system infected by Qhost?

Stop the DNS cache service (net stop dnscache), reset %windir%\system32\drivers\etc\hosts to defaults, restart dnscache, and execute a full antivirus scan.

How do I remove the Qhost Trojan from Windows?

Manual removal of Qhost is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Qhost a virus or a Trojan?

Qhost is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Qhost typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Qhost infection?

Symptoms of Qhost can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Trojans

Want to prevent Qhost and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/qhost.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.